Requesting a mobile device for a person

4.6 Requesting a mobile device for a person

See the Mobile Identity Management guide for details of configuring your system to issue mobile devices.

4.6.1 Requesting a mobile device

To request a mobile device for a person:

Search for a person, and view their details.

See section 4.1, Searching for a person for details.

You can also view a person's details from any form that contains a link to their account.

For example:
- Click the link icon on the Full Name field of the View Request form.
- Click the link icon on the Owner field of the View Device form.
Click one of the following options in the button bar at the bottom of the screen:
- Request Mobile – requests a mobile device for the person.
- Request Mobile (View Auth Code) – requests a mobile device for the person, and displays the collection URL and authentication code for the device on the View Request screen at the end of the process.
You may have to click the ... option to see any additional available actions.

The Request Mobile Issuance screen appears.
From the Credential Profile drop-down list, select the credential profile you want to use for the device.

The credential profile must have a Card Encoding setting of Identity Agent.

See the Creating the Identity Agent credential profile section in the Mobile Identity Management guide for details.
Optionally, in the Label box, type a label for this request.

You can use the label to search for the request:
- In the Requests search form, select Label from the additional search criteria.
  
  See section 6.1, Searching for a request.
- In MyID Desktop, in the Job Management workflow, use the Batch Label box.
  
  See the Searching for jobs section in the Administration Guide.
Optionally, set the Maximum Expiry Date.

This option is available only if the Set expiry date at request option (on the Issuance Processes page of the Operation Settings workflow) is set to Yes.

The maximum expiry date is the requested date on which the device will expire. You can select any date up to the MaxRequestExpiryDate specified for the person in the Lifecycle API. Note, however, that you cannot exceed the Lifetime setting for the credential profile; if the request is made for a credential to expire on a date six months from now, but the credential profile has a lifetime of 30 days, the device will be issued with a lifetime of 30 days.

The credential profile can override the MaxRequestExpiryDate set for the person if the Ignore User Expiry Date option on the credential profile is set.

Note: If the Expire cards at end of day configuration option (on the Issuance Processes page of the Operation Settings workflow) is set to Yes, the requested date will be 23:59 UTC on the date selected. See the Issuance Processes page (Operation Settings) section in the Administration Guide.
Click SAVE to make the request.

Once you have created the request, the View Request screen appears. From this screen, you can cancel the device request. If the request requires validation, another operator must approve the request; the operator who makes a request cannot validate it. See section 6.2, Approving, rejecting, and canceling requests.

Once the request is ready for collection (after approval, if necessary), MyID sends the collection URL and an authentication code to the person for whom the device was requested; see the Configuring SMS and email notifications for the MyID Operator Client section in the Mobile Identity Management guide for details

As an alternative to sending the collection URL and authentication code as notifications, you can use the Request Mobile (View Auth Code) option instead; when you use this option, the following additional information is provided on the View Request screen:

Collection URL – The URL that the person must access on their mobile device to collect the mobile device.
Authentication Code – The authentication code that the person must provide to collect the mobile device.

You can provide these details to the person manually; this is an alternative to using email and SMS notifications to provide this information. If the credential profile requires validation, make sure that the request has been validated before you provide the information to the person; if you use email and SMS notifications, then these are not sent until the request has been validated.

Note: These fields are displayed only once, at the end of the Request Mobile (View Auth Code) operation; if you view the request again, you will not be able to view this information.

4.6.2 Requesting mobile devices for multiple people

If you want to request mobile devices for multiple people, you can request the mobile devices in a batch instead of requesting them one by one.

To request mobile devices for multiple people:

Search the directory for the people for whom you want to request mobile devices.

See section 4.1, Searching for a person.
On the search results page, use the checkboxes to the left of the records to select one or more people.

Note: If you select one person, the process is the same as clicking the Request Mobile option in the button bar at the bottom of the View Person screen; MyID uses the batch process only if you select more than one person. See section 4.6.1, Requesting a mobile device for details of requesting a single device.
From the Tools menu, select Request Mobile.

The Request Mobile Issuance screen appears.

Complete the details as for requesting a device for a single person, including the credential profile to be used for the requested devices; see section 4.6.1, Requesting a mobile device.
Click Save.

The confirmation screen appears.
Click Yes to proceed with the request, or No to go back to the list of people.

When you click Yes, the Batch Processing screen appears.

The requests are processed. The table shows the status of each request:

	The request succeeded.
	The request failed. The Message column displays the reason for the failure; for example, the person may not have permissions for the credential profile selected.

Click Close.